This was something that existed for some scripting support for a totally
unrelated project and when I copied this script I failed to remove it so
this removes it. Build containers for Xen are best as ephemeral
environments and should just utilizes Docker's default container naming
behavior.
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Reviewed-by: Wei Liu <wei.liu2@citrix.com>
- XEN_CONFIG_EXPERT: If this is defined in your shell it will be
automatically passed through to the container.
-- CONTAINER_NAME: By default the container name is set based on the
- container itself so that its easy to attach other terminals to your
- container. This however prevents you from running multiple containers
- of the same version. Override the name value to cause it to name
- the container differently on start.
Building a container
--------------------
fi
fi
-# if we got the CONTAINER_NAME env variable then use that for our name
-if [[ -n ${CONTAINER_NAME} ]]; then
- name="--name ${CONTAINER_NAME}"
-fi
-
# Figure out the base of what we want as our sources
# by using the top of the git repo
if [[ -z ${CONTAINER_PATH} ]]; then
-v "${HOME}/.ssh":/root/.ssh:ro \
${SSH_AUTH_DIR:+-v "${SSH_AUTH_DIR}":/tmp/ssh-agent} \
${XEN_CONFIG_EXPERT:+-e XEN_CONFIG_EXPERT=${XEN_CONFIG_EXPERT}} \
- ${CONTAINER_ARGS} ${name} \
+ ${CONTAINER_ARGS} \
-${termint}i --rm -- \
${CONTAINER} \
${cmd}